feat(textrazor): textrazor Plugin - #1036

@Simran-Sharma392 is attempting to deploy a commit to the corsair Team on Vercel.

A member of the Team first needs to authorize it.

No actionable comments were generated in the recent review. 🎉

sequenceDiagram
  participant Caller
  participant analyzeContent
  participant textrazorCall
  participant TextRazorAPI
  participant EntityStore
  participant EventLogger
  Caller->>analyzeContent: provide text or URL and extractors
  analyzeContent->>textrazorCall: submit analysis form
  textrazorCall->>TextRazorAPI: send authenticated request
  TextRazorAPI-->>textrazorCall: return analysis response
  textrazorCall-->>analyzeContent: return validated response
  analyzeContent->>EntityStore: cache extracted entities
  analyzeContent->>EventLogger: log completed operation
  analyzeContent-->>Caller: return filtered result

• Fix all pre-merge checks with AI

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands.}

Greptile Summary

The PR adds and registers a TextRazor integration with API-key authentication, validated NLP and account operations, and custom dictionary and classifier management.

• Adds TextRazor request handling, error classification, and endpoint registration.
• Defines Zod contracts for analysis, account, dictionary, and classifier operations.
• Adds endpoint routing, schema, authentication, and error-policy tests.
• The latest changes complete the previously requested list response and item-identity validation.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Caller[Caller] --> Plugin[TextRazor plugin]
  Plugin --> Input[Zod input validation]
  Input --> Endpoint[Endpoint handler]
  Endpoint --> Client[TextRazor client]
  Client --> API[TextRazor API]
  API --> Client
  Client --> Output[Zod output validation]
  Output --> Caller

_{Reviews (3): Last reviewed commit: "fix(textrazor): require ids on dictionar..." | Re-trigger Greptile}

Plugin PR scorecard — packages/textrazor

Rules: PLUGIN_PR_RULES.md · re-runs on every push

Hey @Simran-Sharma392, thanks for the contribution! 🏴‍☠️ Before a maintainer reviews, please fix the items below — the review re-runs automatically on your next push.

Must fix

• P1 packages/textrazor/endpoints/types.ts:285 — List Validation Is Bypassed
  When TextRazor returns a malformed dictionary or classifier list payload, the z.unknown() response schemas accept it unchanged, causing invalid data to pass through the public endpoint contract and fail later in callers.

Rule Used: Every endpoint must validate inputs and outputs wi... (source)

Knowledge Base Used: Provider plugin implementation conventions

If anything remains after your next push, a maintainer will take it from there and do the final review and merge.

@greptile

Maintainer review needed

Automated rounds are exhausted. Remaining findings:

• P1 packages/textrazor/endpoints/types.ts:252 — List items remain unvalidated
  When TextRazor returns a list containing {} or an object with only unrecognized properties, these all-optional item schemas accept it and the list endpoints return an identity-less entry to callers, leaving the public list contract unable to reject malformed items.

@greptile